Web objects in stateless and state-persistent contexts
Figure 7–1 illustrates how a stateless Web object may run in a state-persistent context during a WebSpeed transaction and also run stateless within a different context.
In this scenario, Web Object X is state-aware while Web Object Y is stateless. At the top of Figure 7–1, Web Object Y is called within the context of a WebSpeed transaction. Web Object Y is still stateless even though it executes on a locked agent because it does not set a time-out period for itself in the transaction. However, Web Object Y does have potential access to the data context established by Web Object X, especially if Web Object Y calls a custom method procedure within Web Object X that returns data from this transaction context. In general, all Web objects that execute on a locked agent participate in the same WebSpeed transaction, whether they are stateless or state aware.
If the client makes a request to Web Object Y (possibly through a different Messenger and WebSpeed broker), Web Object Y executes as a stateless Web object on WebSpeed agent B. Here the Web object also runs stateless, but with no underlying transaction context available.